Separate cryptographic keys for protecting different operations on data

ABSTRACT

The disclosed embodiments provide a system that processes data. During operation, the system uses a first key to protect a write operation on the data. Next, the system uses a second key to protect a read operation on the data.

BACKGROUND Field

The disclosed embodiments relate to techniques for protecting data. Morespecifically, the disclosed embodiments relate to techniques for usingseparate cryptographic keys for protecting different operations on thedata, such as read operations and write operations.

Related Art

Data on network-enabled electronic devices is frequently stored, shared,and/or backed up using remote storage mechanism such as file hostingservices, cloud storage services, and/or remote backup services. Forexample, a user may use a cloud storage service to store and/or back upa file on a personal computer, laptop computer, portable media player,personal digital assistant, tablet computer, and/or smart phone. Afterthe file is uploaded to the cloud storage service, the user may retrievethe file and/or share the file with other users from the cloud storageservice.

However, storage of data on untrusted remote storage mechanisms may beassociated with a number of security issues. First, the data may beaccessed by an unauthorized third party, thus compromising theconfidentiality of the data. For example, the data may be obtained by anattacker if the attacker steals authentication credentials for accessingthe data on cloud storage and/or reads packets containing the dataduring writing of the data to cloud storage and/or reading of the datafrom cloud storage. Second, the unauthorized third party may compromisethe integrity of the data by modifying and/or tampering with the data.For example, an attacker may inject packets into a network connectionbetween a user writing the data and cloud storage, resulting in storingof the packets' payloads with the data on the cloud storage and/orsubsequent reading of the stored payloads from the cloud storage by theuser and/or other users.

Hence, use of untrusted remote storage mechanisms may be facilitated bysecuring both the storage of data on the remote storage mechanisms andthe transmission of the data between the remote storage mechanisms andnetwork-enabled electronic devices.

SUMMARY

The disclosed embodiments provide a system that processes data. Duringoperation, the system uses a first key to protect a write operation onthe data. Next, the system uses a second key to protect a read operationon the data.

In some embodiments, the system also uses a third key to protect thewrite operation on metadata for the data and uses a fourth key toprotect the read operation on the metadata.

In some embodiments, using the first key to protect the write operationinvolves using a data key to encrypt the data, and using the first keyto generate a signature associated with the data. For example, the datakey may be a symmetric key, and the first key may be a private key thatis part of a asymmetric private/public key pair. The first key may alsobe used to encrypt the symmetric key.

In some embodiments, using the second key to protect the read operationinvolves using the data key to decrypt the data, and using the secondkey to verify the signature. For example, the second key may be a publickey that is part of the same asymmetric private/public key pair as thefirst key. The second key may also be used to decrypt the encryptedsymmetric key prior to decrypting the data with the symmetric key.

In some embodiments, the first and second keys are associated with atleast one of a file, a set of files, and a user.

In some embodiments, the data key is associated with at least one of ablock and a file.

In some embodiments, using the first key to protect the write operationfurther involves appending an amount of padding in the encrypted data tothe encrypted data.

In some embodiments, the write operation is protected prior toperforming the write operation with a remote storage mechanism, and theread operation is protected after performing the read operation with theremote storage mechanism.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 shows a schematic of a system in accordance with the disclosedembodiments.

FIG. 2 shows a system for processing data in accordance with thedisclosed embodiments.

FIG. 3 shows a flowchart illustrating the processing of data inaccordance with the disclosed embodiments.

FIG. 4 shows a computer system in accordance with the disclosedembodiments.

In the figures, like reference numerals refer to the same figureelements.

DETAILED DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the embodiments, and is provided in the contextof a particular application and its requirements. Various modificationsto the disclosed embodiments will be readily apparent to those skilledin the art, and the general principles defined herein may be applied toother embodiments and applications without departing from the spirit andscope of the present disclosure. Thus, the present invention is notlimited to the embodiments shown, but is to be accorded the widest scopeconsistent with the principles and features disclosed herein.

The data structures and code described in this detailed description aretypically stored on a computer-readable storage medium, which may be anydevice or medium that can store code and/or data for use by a computersystem. The computer-readable storage medium includes, but is notlimited to, volatile memory, non-volatile memory, magnetic and opticalstorage devices such as disk drives, magnetic tape, CDs (compact discs),DVDs (digital versatile discs or digital video discs), or other mediacapable of storing code and/or data now known or later developed.

The methods and processes described in the detailed description sectioncan be embodied as code and/or data, which can be stored in acomputer-readable storage medium as described above. When a computersystem reads and executes the code and/or data stored on thecomputer-readable storage medium, the computer system performs themethods and processes embodied as data structures and code and storedwithin the computer-readable storage medium.

Furthermore, methods and processes described herein can be included inhardware modules or apparatus. These modules or apparatus may include,but are not limited to, an application-specific integrated circuit(ASIC) chip, a field-programmable gate array (FPGA), a dedicated orshared processor that executes a particular software module or a pieceof code at a particular time, and/or other programmable-logic devicesnow known or later developed. When the hardware modules or apparatus areactivated, they perform the methods and processes included within them.

FIG. 1 shows a schematic of a system in accordance with an embodiment.As shown in FIG. 1, the system includes an administration server 100,storage 110, an active directory server 120, a set of computers 130-140,a network 150, and a portable storage device 160. Each of the componentsis described in further detail below.

Computers 130-140 may correspond to electronic devices that may be usedto perform tasks for users of computers 130-140. For example, eachcomputer 130-140 may correspond to a personal computer (PC), laptopcomputer, and/or workstation. Network 150 may correspond to a computernetwork, such as a local area network (LAN), wide area network (WAN),wireless network, intranet, internet, and/or another type of networkthat facilitates communication among devices (e.g., administrationserver 100, storage 110, active directory server 120, computers 130-140)connected to network 150. For example, computers 130-140 may operate asclients in network 150 and allow users of computers 130-140 to send andreceive emails, retrieve web pages, and/or send and receive files withother computers and/or servers (e.g., administration server 100, activedirectory server 120) on network 150.

Computers 130-140 may serve as host computing resources and environmentsfor guest virtual computing environments. In one or more embodiments,the virtual computing environments correspond to virtual machines thatexecute operating systems locally on computers 130-140, but in isolationfrom other virtual machines and host computing environments (e.g.,native operating systems) on computers 130-140. The virtual computingenvironments may also provide other types of virtualization to users ofcomputers 130-140, such as application virtualization and/or resource(e.g., network, memory, storage, processor, etc.) virtualization. Forexample, computer 130 may include three virtual computing environmentsrespectively running Linux, Mac OS X (OS X™ is a registered trademark ofApple Inc.), and Microsoft Windows (Microsoft Windows™ is a registeredtrademark of Microsoft Corp.). Applications and/or processes that arespecific to an operating system may thus run on computers 130-140 withinthe virtual computing environment containing the operating system. Inother words, the execution of one or more virtual computing environmentson computers 130-140 may provide increased versatility, utilization ofresources, and/or security to computers 130-140. Software such as VMwareWorkstation (Windows), VMware Fusion (Mac) (VMware Fusion™ is aregistered trademark of VMware, Inc.), Parallels, and VirtualBox(VirtualBox™ is a registered trademark of Oracle America, Inc.) may beused to provide these capabilities.

In one or more embodiments, the system of FIG. 1 enables the centralmanagement and local execution of virtual computing environments. Suchcentral management and local execution may allow the virtual computingenvironments to be configured from a central location and efficientlydeployed to multiple users from the central location. Moreover, changesand updates to the virtual computing environments may be automaticallypropagated to the users from the central location, resulting insignificant savings in time and resources. An example of a centralmanagement solution for locally executed virtual computing environmentsmay include the MokaFive Server, Player and Creator products offered byMokaFive (moka5, Inc., a Delaware corporation). In particular, theMokaFive Player may be used with computers 130-140 to locally execute acentrally defined and managed virtual computing environment according torules and access controls defined in the MokaFive Server.

Administration server 100 may be a server that supports centralizeddefinition of virtual computing environments and management of accessand permissions to the same for local execution. For example,administration server 100 may be provided by the MokaFive Server.Administration server 100 may itself execute in a virtual computingenvironment, such as a VMware ESX environment. An administrator ofvirtual computing environments for computers 130-140 may create,configure, and delete the virtual computing environments by interactingwith administration server 100 through a management interface (e.g.,graphical user interface (GUI), web-based user interface, etc.) providedby administration server 100.

Active directory server 120 may provide network-based directoryservices. For example, active directory server 120 may be a MicrosoftActive Directory (Active Directory™ is a registered trademark ofMicrosoft Corp.) Domain Controller, OpenLDAP server, OpenID, and/oranother commercially available directory server. More specifically,active directory server 120 may store, organize, and provide access tousers, groups, and permissions associated with virtual computingenvironments managed through administration server 100. For example,active directory server 120 may enable a hierarchical framework ofservices (e.g., virtual computing environments) and users (e.g., useraccounts and groups) within network 150 to be used by administrationserver 100 in defining access permissions and policies to virtualcomputing environments.

In one or more embodiments, virtual computing environments executed oncomputers 130-140 are stored in storage 110. Storage 110 may correspondto network attached storage (NAS), a web server with attached storage, astorage area network (SAN), and/or another storage mechanism that isaccessible through network 150. Computers 130-140 may obtain the virtualcomputing environments from storage 110 through network 150 and executethe virtual computing environments locally to enable users of computers130-140 to interact with the virtual computing environments.

To access the virtual computing environments, each computer 130-140 mayinclude one or more subscriptions to virtual computing environmentsstored in storage 110. Each subscription may identify administrationserver 100 and a specific virtual computing environment provided byadministration server 100. To execute the virtual computing environment,a user of the computer may provide authentication credentials for thevirtual computing environment to administration server 100, which mayrelay the authentication credentials to the active directory server 120as necessary. If the user is authorized to use the virtual computingenvironment, the virtual computing environment is downloaded fromstorage 110 over network 150 and loaded on the computer for use by theuser.

In one or more embodiments, virtual computing environments on computers130-140 are stored in layered filesystems. The layered filesystems mayseparate different components of the virtual computing environments intoindividually managed layers based on policies for the layeredfilesystems. In one or more embodiments, each layered filesystemincludes a system layer that stores an image of a virtual computingenvironment obtained from storage 110 and/or administration server 100.The layered filesystem may also include an application layer for storinguser-installed applications, as well as a user data layer for storinguser-specific documents and settings.

The layered filesystems may further facilitate the management of thevirtual computing environments by enabling individual layers to beadded, removed, temporarily disabled, and/or restored. In particular,the system layer may be periodically populated with a new image of thevirtual computing environment from storage 110 and/or administrationserver 100. As a result, computers 130-140 may always execute the mostup-to-date versions of the virtual computing environments. Furthermore,the application layer may be removed or temporarily disabled if a virusor malfunctioning application is installed in the application layer.Snapshots or backups of individual layers may additionally enhance thesecurity, reliability, and integrity of the virtual computingenvironments. Management and execution of virtual computing environmentsusing layered filesystems is described in a co-pending non-provisionalapplication by inventors Thomas Joseph Purtell II and John Whaley,entitled “Policy-Based Layered Filesystem Management,” having Ser. No.12/435,279, and filing date 4 May 2009, which is incorporated herein byreference.

As described in the above-referenced applications, data created using avirtual computing environment may be stored in a separate layer of afilesystem than the operating system and/or applications in the virtualcomputing environment. The data may also be stored and/or backed up onnetwork-based storage (e.g., storage 110) to enable recovery of the dataand/or access to the data outside the virtual computing environment. Forexample, the data may be an image, document, audio, video, and/or othertype of file that is created on and/or used with a virtual computingenvironment. Moreover, saving of the data within the virtual computingenvironment may cause the data to be transmitted from the virtualcomputing environment to cloud storage. The data may be then persistedon the cloud storage and/or downloaded to electronic devices that areauthorized to access the data.

However, the network-based storage may be untrusted and/or insecure,thus exposing the data to increased risk of unauthorized access and/ortampering. Continuing with the above example, an attacker may interceptand/or modify the data during transmission of the data from the virtualcomputing environment to the network-based storage (e.g., during“writing” of the data to the network-based storage) and/or from thenetwork-based storage to an electronic device authorized to access thedata (e.g., during “reading” of the data from the network-basedstorage). Alternatively, the attacker may gain access to the stored databy obtaining authentication credentials for a user account associatedwith the data on the network-based storage and providing theauthentication credentials to the network-based storage.

In one or more embodiments, access to and/or storage of data onuntrusted and/or third party network-based storage is secured byencrypting the data before the data is transmitted (e.g., written) tothe network-based storage and decrypting the data after the data isobtained (e.g., read) from the network-based storage. In addition,different cryptographic keys may be used to protect reading and writingof the data and/or metadata for the data. Such use of separate keys withoperations, data, and/or metadata may protect the data and/or metadatafrom unauthorized access and/or modification while enabling fine-grainedaccess control to the data and/or metadata by authorized users, asdiscussed in further detail below with respect to FIG. 2.

FIG. 2 shows a system for processing data 210 in accordance with thedisclosed embodiments. More specifically, FIG. 2 shows a system forprotecting data 210 during use of the data with a potentially insecurestorage mechanism 206.

Data 210 may be written to storage mechanism 206 from a write-managementapparatus 202 and read from storage mechanism 206 using aread-management apparatus 204. For example, write-management apparatus202 may be associated with an application and/or virtual computingenvironment used to create and/or store the data on a personal computer,laptop computer, tablet computer, portable media player, digital mediareceiver, and/or other network-enabled electronic device. To facilitaterecovery of and/or access to data 210, write-management apparatus 202may transmit data 210 to a network-accessible storage mechanism 206 suchas storage 110 of FIG. 1, NAS, a SAN, a server with attached storage,and/or cloud storage. After data 210 is stored on storage mechanism 206,read-management apparatus 204 may obtain data 210 from storage mechanism206 for use with the same electronic device and/or a differentelectronic device.

Prior to transmitting data 210 to storage mechanism 206 (e.g.,performing a write operation with storage mechanism 206),write-management apparatus 202 may encrypt data 210 so that data 210 istransmitted to storage mechanism 206 and stored on storage mechanism 206as encrypted data 212. Encrypted data 212 may then be transmitted fromstorage mechanism 206 to read-management apparatus 204, which decryptsencrypted data 212 to obtain decrypted data 214 that is identical todata 210 (e.g., after performing a read operation on encrypted data 212with storage mechanism 206). In other words, write-management apparatus202 and read-management apparatus 204 may protect data 210 fromunauthorized access by enabling the transmission and storage ofencrypted data 212 instead of unencrypted data 210, as well as use ofdecrypted data 214 by users authorized to access data 210.

More specifically, a data key 230 and/or other keys used to protect data210 may be provided to write-management apparatus 202 and/orread-management apparatus 204 by a key-management apparatus 208. Forexample, key-management apparatus 208 may be a server, such asadministration server 100 and/or active directory server 120 of FIG. 1,that selects keys used in protecting data 210 and/or other dataassociated with storage mechanism 206 and transmits the keys towrite-management apparatus 202 and/or read-management apparatus 204.Write-management apparatus 202 may use data key 230 to encrypt data 210,and read-management apparatus 204 may use the same data key 230 togenerate decrypted data 214 from encrypted data 212. Data key 230 maythus be a symmetric key that enables efficient encryption and decryptionof data 210.

To protect data 210 from tampering and/or unauthorized modification,key-management apparatus 208, write-management apparatus 202, and/orread-management apparatus 204 may use different keys to protect writeoperations and read operations on data 210. As shown in FIG. 2,write-management apparatus 202 may use a write key 222 from managementapparatus 208 to protect a write operation on data 210, whileread-management apparatus 202 may use a read key 226 from managementapparatus 208 to protect a read operation on data 210.

In particular, write-management apparatus 202 may obtain write key 222as a private key in an asymmetric private/public key pair and use writekey 222 to generate a signature 234 associated with data 210. Signature234 may be generated from data 210, a hash value computed from data 210,and/or another representation of data 210 and transmitted to storagemechanism 206 along with encrypted data 212 during writing of data 210to storage mechanism 206. Next, read-management apparatus 204 may obtainread key 226 as a public key in the asymmetric private/public key pairand use read key 226 to generate a verification 238 of signature 234during reading and/or decryption of encrypted data 212. In other words,write key 222 may be used to write data 210 that can be verified, andread key 226 may be used to verify the authenticity and/or integrity ofdata 210.

Write key 222 may additionally and/or alternatively be used to encryptdata key 230 and store the encrypted data key 230 along with encrypteddata 212 during the write operation. Read key 226 may then be used todecrypt the encrypted data key 230, and the decrypted data key 230 maybe used to decrypt encrypted data 212. Consequently, write key 222 andread key 226 may be used to securely share data key 230 betweenwrite-management apparatus 202 and read-management apparatus 204 in theabsence of a central management apparatus 208 for providing keysassociated with protecting data 210.

As shown in FIG. 2, an amount of padding 238 may also be stored withencrypted data 212 and/or signature 234 in storage mechanism 206.Write-management apparatus 204 may determine amount of padding 238 byperforming a modulo operation of the length of data 210 with the blocksize used to encrypt data 210, and subtracting the result of the modulooperation from the block size. Write-management apparatus 204 may thenappend amount of padding 238 to encrypted data 218 (e.g., as a sequenceof 0's) for storage in storage mechanism 206. Read-management apparatus204 may subsequently obtain amount of padding 238 with encrypted data212 by performing a modulo operation of the length of encrypted data 212and use amount of padding 238 to determine the original size of data 210without decrypting encrypted data 212.

To further protect and/or manage access to data 210, write-managementapparatus 202 and read-management apparatus 204 may use a different setof keys to protect operations on metadata 216 for data 210, which mayinclude a filename associated with data 210, a path for data 210, and/orother information related to data 210. For example, write-managementapparatus 202 may use a metadata key 232 to encrypt metadata 216 beforewriting metadata 216 to storage mechanism 206 so that metadata 216 isstored as encrypted metadata 218 in storage mechanism 206.Write-management apparatus 202 may also use a different write key 224 togenerate an encrypted metadata key and/or signature 236 associated withmetadata 236 for storage along with encrypted metadata 218 in storagemechanism 206. In turn, read-management apparatus 204 may use metadatakey 232 to generate decrypted metadata 220 from encrypted metadata 218after reading encrypted metadata 218 from storage mechanism 208.Read-management apparatus 204 may also use a different read key 228 togenerate a verification 240 of signature 236 and/or decrypt metadata key232.

By using different keys to protect different operations (e.g., readoperations, write operations, etc.) on data 210, the system of FIG. 2may maintain the confidentiality and integrity of data 210. For example,the system of FIG. 2 may prevent an attacker from obtaining data 210during transmission of packets containing encrypted data 212 betweenstorage mechanism 206 and/or one or more electronic devices associatedwith write-management apparatus 202 and/or read-management apparatus204. In addition, the encryption, decryption, and/or verification ofdata 210 independently from the use of storage mechanism 206 to storedata 210 (e.g., as encrypted data 212) may allow data 210 to beprotected even if the attacker gains direct access to storage mechanism206 (e.g., by exploiting a vulnerability associated with storagemechanism 206).

Moreover, the use of different sets of keys for data 210 and metadata216 may enable fine-grained access control for both data 210 andmetadata 216. For example, both write key 222 and read key 226 may begiven to a user with permission to write and/or modify data 210, whileonly read key 226 may be provided to a user with permission to read data210. Along the same lines, write key 224 and/or read key 228 may beprovided to a less trusted user to enable access to metadata 216 (e.g.,for use in analytics related to data 210) and/or modification ofmetadata 216 (e.g., renaming of and/or relocating a file containing data210) by the user without granting access to data 210 for the user.

To further manage, track, and/or protect access to data 210 and/ormetadata 216, the system of FIG. 2 may apply write keys 222-224, readkeys 226-228, and/or data key 230 and metadata key 232 to differenttypes and/or amounts of data 210 and/or metadata 216. First, data key230 and/or metadata key 232 may be applied to a block and/or a fileassociated with data 210 and/or metadata 216. For example, data key 230may be used to encrypt and decrypt an entire file containing data 210,or individual blocks in the file may be encrypted and/or decrypted in around-robin fashion using data key 230 and a set of other data keys.Second, write keys 222-224 and read keys 226-228 may be associated witha file, a set of files, and/or a user. For example, read and/or writeaccess to the file and/or a directory containing one or more files maybe granted to a set of users by assigning the same read and/or write keyto the file and/or directory. On the other hand, tracking ofmodifications to the file by the user and/or other users may be enabledby assigning each user with permission to write to the file a differentread/write key pair and/or using a different read/write key pair foreach modification to the file.

Those skilled in the art will appreciate that the system of FIG. 2 maybe implemented in a variety of ways. As mentioned above,write-management apparatus 202 and read-management apparatus 204 mayreside on the same electronic device and/or different electronicdevices. For example, write-management apparatus 202 and read-managementapparatus 204 may be used by an application and/or virtual computingenvironment on a laptop computer to securely store, access, and/orupdate a file stored on a remote storage mechanism 206. Alternatively,write-management apparatus 202 may be used to perform and protectwriting of the file to storage mechanism 206 from the laptop computer,and read-management apparatus 204 may be used to perform and protectreading of the file from storage mechanism 206 on a tablet computer,provided the user of the tablet computer is authorized to read the file.

Moreover, write-management apparatus 202 and read-management apparatus204 may use different types and/or combinations of cryptographictechniques to protect operations associated with data 210 and metadata216. For example, the techniques described above for protecting read andwrite operations on data 210 and metadata 216 may be used with salts,different types of encryption, initialization vectors, prevention ofrollback attacks, and/or other techniques for securing data.

Finally, the functionality of key-management apparatus 208 may beimplemented using various techniques and/or devices. As described above,key-management apparatus 208 may be a centralized server that selectskeys for use with different groups and/or types of users, data, and/ormetadata and provides the keys to write-management apparatus 202 andread-management apparatus 204 for use in protecting read and writeoperations associated with the users, data, and/or metadata. Conversely,key-management apparatus 208 may be implemented in a decentralizedmanner by write-management apparatuses (e.g., write-management apparatus202) and read-management apparatuses (e.g., read-management apparatus204) associated with different applications, users, and/or electronicdevices. To facilitate secure transmission of data keys (e.g., data key230, metadata key 232) among the write-management apparatuses andread-management apparatuses, each write-management apparatus may encrypta data key using a write key and transmit the encrypted data key to aread-management apparatus. The read-management apparatus may then usethe read key corresponding to the write key to decrypt the data key forsubsequent use in decrypting data and/or metadata encrypted using thedata key.

FIG. 3 shows a flowchart illustrating the processing of data inaccordance with the disclosed embodiments. In one or more embodiments,one or more of the steps may be omitted, repeated, and/or performed in adifferent order. Accordingly, the specific arrangement of steps shown inFIG. 3 should not be construed as limiting the scope of the technique.

Initially, a first key is used to protect a write operation on the data(operation 302), and a second key is used to protect a read operation onthe data (operation 304). The write and read operations may be performedwith network-accessible storage such as untrusted and/or third partycloud storage. To protect the write operation, the data may be encryptedusing a data key (e.g., a symmetric key), and a signature for the datamay be generated using the first key (e.g., a private key from apublic/private key pair). The amount of padding in the encrypted datamay also be appended to the encrypted data to enable calculation of theoriginal length of the data without decrypting the data. To protect theread operation, the data key may be used to decrypt the data, and thesignature for the data may be verified using the second key (e.g., apublic key from the public/private key pair).

Different keys may also be used with metadata (operation 306) for thedata. For example, the metadata may be encrypted and/or decrypted usingdifferent keys than the data to enable read and/or write access to themetadata independently from read and/or write access to the data. Ifdifferent keys are not used with the metadata, read and write operationson the metadata may be protected using the same keys as read and writeoperations on the data.

If different keys are used with the metadata, a third key is used toprotect a write operation on the metadata (operation 308), and a fourthkey is used to protect a read operation on the metadata (operation 310).For example, the metadata may be encrypted using a metadata key (e.g., asymmetric key), and a signature for the metadata may be generated usingthe third key (e.g., a private key from a public/private key pair). Anypadding used in encrypting the metadata may also be indicated byappending the amount of padding in the encrypted metadata to theencrypted metadata. The metadata key may then be used to decrypt thedata, and the signature for the metadata may be verified using thefourth key (e.g., a public key from the public/private key pair).

FIG. 4 shows a computer system 400 in accordance with the disclosedembodiments. Computer system 400 includes a processor 402, memory 404,storage 406, and/or other components found in electronic computingdevices. Processor 402 may support parallel processing and/ormulti-threaded operation with other processors in computer system 400.Computer system 400 may also include input/output (I/O) devices such asa keyboard 408, a mouse 410, and a display 412.

Computer system 400 may include functionality to execute variouscomponents of the present embodiments. In particular, computer system400 may include an operating system (not shown) that coordinates the useof hardware and software resources on computer system 400, as well asone or more applications that perform specialized tasks for the user. Toperform tasks for the user, applications may obtain the use of hardwareresources on computer system 400 from the operating system, as well asinteract with the user through a hardware and/or software frameworkprovided by the operating system.

In one or more embodiments, computer system 400 provides a system forprocessing data. The system may include a write-management apparatusthat uses a first key to protect a write operation on the data. Thesystem may also include a read-management apparatus that uses a secondkey to protect a read operation on the data. The write-managementapparatus may also use a third key to protect the write operation onmetadata for the data, and the read-management apparatus may use afourth key to protect the read operation on the metadata. Finally, thesystem may include a key-management apparatus that provides one or moreof the keys to the write-management apparatus and/or read-managementapparatus.

In addition, one or more components of computer system 400 may beremotely located and connected to the other components over a network.Portions of the present embodiments (e.g., write-management apparatus,read-management apparatus, key-management apparatus, etc.) may also belocated on different nodes of a distributed system that implements theembodiments. For example, the present embodiments may be implementedusing a cloud computing system that manages the protection of write andread operations on data and/or metadata associated with a set of remoteelectronic devices.

The foregoing descriptions of various embodiments have been presentedonly for purposes of illustration and description. They are not intendedto be exhaustive or to limit the present invention to the formsdisclosed. Accordingly, many modifications and variations will beapparent to practitioners skilled in the art. Additionally, the abovedisclosure is not intended to limit the present invention.

What is claimed is:
 1. A method, comprising: using a first key toprotect a write operation on data by encrypting, by a computer, the datawith a data key; and using a second key to protect a read operation onthe data by decrypting the data with the data key; wherein using thefirst key to protect the write operation further involves appending anamount of padding in the encrypted data to the encrypted data; whereinan amount of padding is determined by performing a modulo operation on alength of the data with a block size and subtracting a result of themodulo operation from the block size.
 2. The method of claim 1,comprising verifying a signature associated with the data with thesecond key, wherein the signature associated with the data is generatedwith the first key.
 3. The method of claim 1, comprising using a thirdkey to protect a write operation on metadata for the data by encryptingthe metadata with a metadata key and generating a signature associatedwith the metadata with the third key.
 4. The method of claim 1, whereinthe block size is used to encrypt the data.
 5. The method of claim 1,wherein the first and second keys are associated with at least one of afile, a set of files, and a user.
 6. The method of claim 1, wherein thedata key is associated with at least one of a block and a file.
 7. Themethod of claim 3, comprising using a fourth key to protect a readoperation on the metadata by decrypting the metadata with the metadatakey.
 8. The method of claim 7, comprising verifying a signatureassociated with the metadata with the fourth key.
 9. A system,comprising: a write-management apparatus configured to: use a first keyto protect a write operation on data by encrypting, by a computer, thedata with a data key; and a read-management apparatus configured to: usea second key to protect a read operation on the data by decrypting thedata with the data key; wherein using the first key to protect the writeoperation further involves appending an amount of padding in theencrypted data to the encrypted data; wherein an amount of padding isdetermined by performing a modulo operation on a length of the data witha block size and subtracting a result of the modulo operation from theblock size.
 10. The system of claim 9, wherein the write-managementapparatus is configured to generate the signature associated with thedata with the first key.
 11. The system of claim 9, wherein thewrite-management apparatus is configured to use a third key to protect awrite operation on metadata for the data via encryption of the metadatawith a metadata key and generate a signature associated with themetadata with the third key.
 12. The system of claim 9, wherein theblock size is used to encrypt the data.
 13. The system of claim 11,wherein the read-management apparatus is configured to use a fourth keyto protect a read operation on the metadata by decrypting the metadatawith the metadata key and verifying a signature associated with themetadata with the fourth key.
 14. The system of claim 9, furthercomprising: a management apparatus configured to: provide the first keyto the write-management apparatus; and provide the second key to theread-management apparatus.
 15. A non-transitory computer-readablestorage medium storing instructions that when executed by a computercause the computer to perform: using a first key to protect a writeoperation on data by encrypting, by a computer, the data with a datakey; and using a second key to protect a read operation on the data bydecrypting the data with the data key; wherein using the first key toprotect the write operation further involves appending an amount ofpadding in the encrypted data to the encrypted data; wherein an amountof padding is determined by performing a modulo operation on a length ofthe data with a block size and subtracting a result of the modulooperation from the block size.
 16. The non-transitory computer-readablestorage medium of claim 15, storing instructions that when executed bythe computer cause the computer to perform generating the signatureassociated with the data with the first key.
 17. The non-transitorycomputer-readable storage medium of claim 15, storing instructions thatwhen executed by the computer cause the computer to perform using athird key to protect a write operation on metadata for the data byencrypting the metadata with a metadata key and generating a signatureassociated with the metadata with the third key.
 18. The non-transitorycomputer-readable storage medium of claim 15, wherein the block size isused to encrypt the data.
 19. The non-transitory computer-readablestorage medium of claim 15: wherein the first and second keys areassociated with at least one of a file, a set of files, and a user, andwherein the data key is associated with at least one of a block and thefile.
 20. The non-transitory computer-readable storage medium of claim15, wherein using the first key to protect the write operation furtherinvolves appending an amount of padding in the encrypted data to theencrypted data.